Magnetic tape rewind overwrite data protection

ABSTRACT

A method for preventing overwriting of data, e.g., on a magnetic medium, includes receiving a write command to write to a magnetic tape. A determination is made as to whether a current location of the magnetic tape is at a block at a beginning of tape. A determination is also made as to whether data corresponding to the write command is at least one of: a size and type specified for the block. Execution of the write command is disallowed when the data corresponding to the write command is not of the specified size and/or type.

BACKGROUND

The present invention relates to data storage systems, and moreparticularly, this invention relates to preventing overwriting of dataon tape by determining a location on tape prior to performing a writeoperation.

Automated data storage libraries are known for providing cost effectivestorage and retrieval of large quantities of data. The data in automateddata storage libraries is typically stored on media of data storagecartridges that are, in turn, stored at storage slots or the like insidethe library in a fashion that renders the media, and its resident data,accessible for physical retrieval. Such data storage cartridges arecommonly termed “removable media.” Data storage cartridge media maycomprise any type of media on which data may be stored and which mayserve as removable media, including but not limited to magnetic media(such as magnetic tape or disks), optical media (such as optical tape ordisks), electronic media (such as PROM, EEPROM, flash PROM,CompactFlash™, Smartmedia™, Memory Stick™, etc.), or other suitablemedia. An example of a data storage cartridge that is widely employed inautomated data storage libraries for mass data storage is a magnetictape cartridge.

The transport of data storage cartridges between data storage sots, datastorage drives, and I/O stations is typically accomplished by one ormore accessors. Such accessors have grippers for physically retrievingthe selected data storage cartridges from the storage slots within theautomated data storage library and transporting such cartridges to thedata storage drives by moving, for example, in the X and Y directions.

In an effort to increase storage capacity, deep slot technology allowsfor storage cells that contain more than a single data storagecartridge. Such storage libraries allow for higher density, or morecartridges stored per square foot. In ‘deep slot’ libraries, two or morecartridges may be stored in a multi-cartridge deep slot cell, arrayed inseries, one behind the other, in tiers ranging from a frontmost tier toa rearmost tier.

In addition to data storage media, automated data storage librariestypically comprise data storage drives that store data to, and/orretrieve data from, the data storage cartridge media. Further, automateddata storage libraries typically comprise I/O stations at which datastorage cartridges are supplied, added to, or removed from, the library.However, conventional products have been unable to protect data writtento data storage cartridges from being overwritten as a result of rewindoperations.

BRIEF SUMMARY

A method according to one embodiment includes receiving a write commandto write to a magnetic tape. A determination is made as to whether acurrent location of the magnetic tape is at a block at a beginning oftape. A determination is also made as to whether data corresponding tothe write command is at least one of: a size and type specified for theblock. Execution of the write command is disallowed when the datacorresponding to the write command is not of the specified size and/ortype.

A system according to one embodiment includes a processor and logicintegrated with and/or executable by the processor. The logic isconfigured to cause the foregoing method to occur.

A computer program product according to one embodiment includes acomputer readable storage medium having program instructions embodiedtherewith, the program instructions readable and/or executable by acontroller to cause the controller to perform the foregoing method.

Any of these embodiments may be implemented in a magnetic data storagesystem such as a tape drive system, which may include a magnetic head, adrive mechanism for passing a magnetic medium (e.g., recording tape)over the magnetic head, and a controller electrically coupled to themagnetic head.

Other aspects and embodiments of the present invention will becomeapparent from the following detailed description, which, when taken inconjunction with the drawings, illustrate by way of example theprinciples of the invention.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a perspective view of an automated data storage libraryaccording to one embodiment.

FIG. 2 is a perspective view of a storage frame from the data storagelibrary of FIG. 1.

FIG. 3 is a block diagram of an automated data storage library accordingto one embodiment.

FIG. 4 is a block diagram depicting a controller configuration accordingto one embodiment.

FIG. 5A is a frontal perspective view of a data storage drive accordingto one embodiment.

FIG. 5B is a rear perspective view of the data storage drive of FIG. 5A.

FIG. 6 is perspective view of a data storage cartridge having a cutawayportion, according to one embodiment.

FIGS. 7A-7B are perspective views of a multi-cartridge deep slot cellaccording to one embodiment.

FIGS. 8A-8D are partial side views of a cartridge blocking mechanismaccording to one embodiment.

FIG. 9 is a flowchart for a method according to one embodiment.

FIG. 10 is a flowchart for a method according to one embodiment.

DETAILED DESCRIPTION

The following description is made for the purpose of illustrating thegeneral principles of the present invention and is not meant to limitthe inventive concepts claimed herein. Further, particular featuresdescribed herein can be used in combination with other describedfeatures in each of the various possible combinations and permutations.

Unless otherwise specifically defined herein, all terms are to be giventheir broadest possible interpretation including meanings implied fromthe specification as well as meanings understood by those skilled in theart and/or as defined in dictionaries, treatises, etc.

It must also be noted that, as used in the specification and theappended claims, the singular forms “a,” “an” and “the” include pluralreferents unless otherwise specified.

The following description discloses several preferred embodiments ofmagnetic storage systems, as well as operation and/or component partsthereof. For example, various embodiments disclosed herein are able toprevent overwriting of data in a tape environment. For example, uponreceiving a write command, various tape drives described below may onlyallow the tape drive to write at the beginning of tape if it is in thetypical size and/or type for a tape label, e.g., to prevent any unwantedoverwrite of data resulting from a tape rewind.

In one general embodiment, a method includes receiving a write commandto write to a magnetic tape. A determination is made as to whether acurrent location of the magnetic tape is at a block at a beginning oftape. A determination is also made as to whether data corresponding tothe write command is at least one of: a size and type specified for theblock. Execution of the write command is disallowed when the datacorresponding to the write command is not of the specified size and/ortype.

In another general embodiment, a system includes a processor and logicintegrated with and/or executable by the processor. The logic isconfigured to cause the foregoing method to occur.

In yet another general embodiment, a computer program product includes acomputer readable storage medium having program instructions embodiedtherewith, the program instructions readable and/or executable by acontroller to cause the controller to perform the foregoing method.

Various embodiments may be implemented in a standalone system, such asin a tape drive that is coupleable to a host. In other approaches, thesystem may be implemented in a larger system, such as in an automateddata storage library or a virtual tape drive.

FIGS. 1-2 illustrate an automated data storage library 10 which storesand retrieves data storage cartridges, containing data storage media(not shown), from multi-cartridge deep slot cells 100 and singlecartridge storage slots 16. An example of an automated data storagelibrary which has a similar configuration as that depicted in FIGS. 1-2,and may be implemented with some of the various approaches herein is theIBM 3584 UltraScalable Tape Library. Moreover, it should be noted thatreferences to “data storage media” herein refer to data storagecartridges, and for purposes of the present application, the two termsmay be used synonymously.

The library 10 of FIG. 1 comprises a left hand service bay 13, one ormore storage frames 11, and right hand service bay 14. As will bediscussed in further detail below, a frame may comprise an expansioncomponent of the library. Thus, storage frames may be added or removedto expand or reduce the size and/or functionality of the library.According to different approaches, frames may include additional storageslots, deep slot cells, drives, import/export stations, accessors,operator panels, etc.

FIG. 2 shows an exemplary embodiment of a storage frame 11, which actsas the base frame of the library 10. Moreover, the storage frame 11illustrated in FIG. 2 is contemplated to be a minimum configuration ofthe library 10, for which there is only a single accessor 18 (i.e.,there are no redundant accessors) and no service bay. However, in otherembodiments, a storage frame may include multiple robotic accessorsand/or service bays.

Looking to FIG. 2, the library 10 is arranged for accessing data storagemedia in response to commands from at least one external host system(not shown). The library 10 includes a plurality of storage slots 16 onfront wall 17 and a plurality of multi-cartridge deep slot cells 100 onrear wall 19, both of which may be used to storing data storagecartridges that may contain data storage media. According to oneapproach, the storage slots 16 are configured to store a single datastorage cartridge, and the multi-cartridge deep slot cells 100 areconfigured to store a plurality of data storage cartridges. In apreferred approach, the multi-cartridge deep slot cells may be arrangedin sequential order of tiers from front to rear (e.g., see FIG. 7A).

With continued reference to FIG. 2, the storage frame 11 of the library10 also includes at least one data storage drive 15, e.g., for readingand/or writing data with respect to the data storage media.Additionally, a first accessor 18 may be used to transport data storagemedia between the plurality of storage slots 16, the multi-cartridgedeep slot cells, and/or the data storage drive(s) 15. According tovarious approaches, the data storage drives 15 may be optical diskdrives, magnetic tape drives, or other types of data storage drives asare used to read and/or write data with respect to the data storagemedia.

As illustrated, the storage frame 11 may optionally include an operatorpanel 23 or other user interface, such as a web-based interface, whichallows a user to interact with the library 10. The storage frame 11 mayalso optionally comprise an upper I/O station 24 and/or a lower I/Ostation 25, thereby allowing data storage cartridges to be added (e.g.,inserted) to the library inventory and/or removed from the librarywithout disrupting library operation. Furthermore, the library 10 mayhave one or more storage frames 11, each having storage slots 16,preferably accessible by the first accessor 18.

As described above, the storage flames 11 may be configured withdifferent components depending upon the intended function. Oneconfiguration of storage frame 11 may comprise storage slots 16 and/ormulti-cartridge deep slot cells 100, data storage drive(s) 15, and otheroptional components to store and retrieve data from the data storagecartridges. However, in another approach, a storage frame 11 may includestorage slots 16 and/or multi-cartridge deep slot cells 100 and no othercomponents. The first accessor 18 may have a gripper assembly 20, e.g.,for gripping one or more data storage media, in addition to having a barcode scanner 22 or other reading system, such as a cartridge memoryreader or similar system mounted on the gripper assembly 20, to “read”identifying information about the data storage media.

FIG. 3 depicts an automated data storage library 10, in accordance withone embodiment. As an option, the present automated data storage library10 may be implemented in conjunction with features from any otherembodiment listed herein, such as those described with reference to theother FIGS. Of course, however, such automated data storage library 10and others presented herein may be used in various applications and/orin permutations which may or may not be specifically described in theillustrative embodiments listed herein. Further, the automated datastorage library 10 presented herein may be used in any desiredenvironment. Thus FIG. 3 (and the other FIGS.) should be deemed toinclude any and all possible permutations.

Referring now to FIG. 3, the automated data storage library 10 asdescribed in reference to FIGS. 1 and 2, is depicted according to oneembodiment. According to a preferred approach, the library 10 may employa controller, e.g., arranged as a distributed system of modules with aplurality of processor nodes as will be discussed in further detailbelow.

According to an exemplary embodiment, an automated data storage librarywhich may implement the distributed system depicted in the block diagramof FIG. 3, and/or other approaches presented herein, is the IBM 3584UltraScalable Tape Library. For a fuller understanding of a distributedcontrol system incorporated in an automated data storage library, referto U.S. Pat. No. 6,356,803, which is entitled “Automated Data StorageLibrary Distributed Control System,” and is hereby incorporated byreference.

While the automated data storage library 10 has been described asemploying a distributed control system, various other approachesdescribed and/or suggested herein may be implemented in automated datastorage libraries regardless of control configuration, such as, but notlimited to, an automated data storage library having one or more librarycontrollers that are not distributed, as that term is defined in U.S.Pat. No. 6,356,803.

Referring still to FIG. 3, the library 10 may have one or more storageframes 11, a left hand service bay 13 and a right hand service bay 14.The left hand service bay 13 is shown with a first accessor 18, where,as discussed above, the first accessor 18 may include a gripper assembly20 and/or a reading system 22 to “read” identifying information aboutthe data storage media depending on the desired embodiment. Furthermore,the right hand service bay 14 is shown having a second accessor 28,which includes a gripper assembly 30 and may also include a readingsystem 32 to “read” identifying information about the data storagemedia.

According to one approach, in the event of a failure or otherunavailability of the first accessor 18, or its gripper assembly 20,etc., the second accessor 28 may perform some or all of the functions ofthe first accessor 18. Thus in different approaches, the two accessors18, 28 may share one or more mechanical paths, they may have completelyindependent mechanical paths, or combinations thereof. In one example,the accessors 18, 28 may have a common horizontal rail with independentvertical rails to travel therealong. Moreover, it should be noted thatthe first and second accessors 18, 28 are described as first and secondfor descriptive purposes only and this description is not meant to limiteither accessor to an association with either the left hand service bay13, or the right hand service bay 14.

In an exemplary embodiment which is in no way intended to limit theinvention, the first and second accessors 18, 28 may preferably movetheir grippers in at least two directions, called the horizontal “X”direction and vertical “Y” direction, e.g., to retrieve and grip,deliver and release, load and unload, etc. the data storage cartridge atthe storage slots 16, multi-cartridge deep slot cells 100, data storagedrives 15, etc.

With continued reference to FIG. 3, library 10 receives commands fromone or more host systems 40, 41, 42. The host systems 40, 41, 42, suchas host servers, communicate with the library directly, e.g., on path80, through one or more control ports (not shown), or through one ormore data storage drives 15 on paths 81, 82. Thus, in differentapproaches, the host systems 40, 41, 42 may provide commands to accessparticular data storage cartridges and move the cartridges, for example,between the storage slots 16 and the data storage drives 15. Thecommands are typically logical commands identifying the cartridges orcartridge media, and/or logical locations for accessing the media.Furthermore, it should be noted that the terms “commands” and “workrequests” are used interchangeably herein to refer to suchcommunications from the host system 40, 41, 42 to the library 10 as areintended to result in accessing particular data storage media within thelibrary 10 depending on the desired approach.

According to one embodiment, the library 10 may be controlled by alibrary controller. Moreover, in various approaches, the librarycontroller may include a distributed control system receiving thelogical commands from hosts, determining the required actions, and/orconverting the actions to physical movements of the first and/or secondaccessor 18, 28. In another approach, the distributed control system mayhave a plurality of processor nodes, each having one or more computerprocessors. According to one example of a distributed control system, acommunication processor node 50 may be located in a storage frame 11.The communication processor node provides a communication link forreceiving the host commands, either directly or through the drives 15,via at least one external interface, e.g., coupled to line 80.

Still referring to FIG. 3, the communication processor node 50 mayadditionally provide a communication link 70 for communicating with thedata storage drives 15. As illustrated, the communication processor node50 may preferably be located in the storage frame 11, e.g., close to thedata storage drives 15. Furthermore, one or more additional workprocessor nodes may be provided to form an exemplary distributedprocessor system, which may comprise, e.g., a work processor node 52located at first accessor 18, and that is coupled to the communicationprocessor node 50 via a network 60, 157. According to differentapproaches, each work processor node may respond to received commandsthat are broadcast thereto from any communication processor node, andthe work processor nodes may also direct the operation of the accessors,e.g., providing move commands. An XY processor node 55 may be providedand may be located at an XY system of first accessor 18. As illustrated,the XY processor node 55 is coupled to the network 60, 157, and isresponsive to the move commands, operating the XY system to position thegripper assembly 20.

Also, an operator panel processor node 59 may be provided at theoptional operator panel 23 for providing an interface for communicatingbetween the operator panel and the communication processor node 50, thework processor nodes 52, 252, and the XY processor nodes 55, 255.

A network 60, for example comprising a common bus, is provided, couplingthe various processor nodes. The network may comprise a robust wiringnetwork, such as the commercially available Controller Area Network(CAN) bus system, which is a multi-drop network, having a standardaccess protocol and wiring standards, for example, as defined by CiA,the CAN in Automation Association, Am Weich Selgarten 26, D-91058Erlangen, Germany. Other networks, such as Ethernet, or a wirelessnetwork system, such as RF or infrared, may be employed in the libraryas is known to those of skill in the art. In addition, multipleindependent networks may also be used to couple the various processornodes.

As illustrated in FIG. 3, the communication processor node 50 is coupledto each of the data storage drives 15 of a storage frame 11, via lines70, and are thereby communicating with the drives 15 and with hostsystems 40, 41, 42. Alternatively, the host systems 40, 41, 42 may bedirectly coupled to the communication processor node 50, at input 80 forexample, or to control port devices (not shown) which connect thelibrary to the host system(s) with a library interface similar to thedrive/library interface. As is known to those of skill in the art,various communication arrangements may be employed for communicationwith the hosts and with the data storage drives. In the example of FIG.3, host connections 80 and 81 are intended to be SCSI busses. However,bus 82 comprises an example of a Fibre Channel bus which is a high speedserial data interface, allowing transmission over greater distances thanthe SCSI bus systems.

According to some approaches, the data storage drives 15 may be in closeproximity to the communication processor node 50, and may employ a shortdistance communication scheme, such as SCSI, or a serial connection,such as RS-422. Thus the data storage drives 15 may be individuallycoupled to the communication processor node 50 by means of lines 70.Alternatively, the data storage drives 15 may be coupled to thecommunication processor node 50 through one or more networks, such as acommon bus network.

Furthermore, additional storage frames 11 may be provided, whereby eachis preferably coupled to the adjacent storage frame. According tovarious approaches, any of the additional storage frames 11 may includecommunication processor nodes 50, storage slots 16, data storage drives15, networks 60, etc.

Moreover, as described above, the automated data storage library 10 maycomprise a plurality of accessors. A second accessor 28, for example, isshown in a right hand service bay 14 of FIG. 3. The second accessor 28may include a gripper assembly 30 for accessing the data storage media,and an XY system 255 for moving the second accessor 28. The secondaccessor 28 may nm on the same horizontal mechanical path as the firstaccessor 18, and/or on an adjacent (e.g., separate) path. Moreover theillustrative control system additionally includes an extension network200 which forms a network coupled to network 60 of the storage frame(s)11 and to network 157 of left hand service bay 13.

In FIG. 3 and the accompanying description, the first and secondaccessors are associated with the left hand service bay 13 and the righthand service bay 14 respectively. However, this is for illustrativepurposes and there may not be an actual association. Thus, according toanother approach, network 157 may not be associated with the left handservice bay 13 and network 200 may not be associated with the right handservice bay 14. Moreover, depending on the design of the library, it maynot be necessary to have a left hand service bay 13 and/or a right handservice bay 14 at all.

An automated data storage library 10 typically comprises one or morecontrollers to direct the operation of the automated data storagelibrary. Moreover, host computers and data storage drives typicallyinclude similar controllers. A library controller may take manydifferent forms and may comprise, for example, but is not limited to, anembedded system, a distributed control system, a personal computer, aworkstation, etc. Essentially, the term “library controller” as usedherein is intended in its broadest sense as a device that contains atleast one computer processor, as such term is defined herein.

Referring now to FIG. 4, a typical controller 400 is shown with aprocessor 402, Random Access Memory (RAM) 403, nonvolatile memory 404,device specific circuits 401, and I/O interface 405. Alternatively, theRAM 403 and/or nonvolatile memory 404 may be contained in the processor402 as could the device specific circuits 401 and I/O interface 405. Theprocessor 402 may comprise, for example, an off-the-shelfmicroprocessor, custom processor, Field Programmable Gate Array (FPGA),Application Specific Integrated Circuit (ASIC), discrete logic, etc. TheRAM 403 is typically used to hold variable data, stack data, executableinstructions, etc.

According to various approaches, the nonvolatile memory 404 may compriseany type of nonvolatile memory such as, but not limited to, ElectricallyErasable Programmable Read Only Memory (EEPROM), flash Programmable ReadOnly Memory (PROM), battery backup RAM, hard disk drives, etc. However,the nonvolatile memory 404 is typically used to hold the executablefirmware and any nonvolatile data. Moreover, the I/O interface 405comprises a communication interface that allows the processor 402 tocommunicate with devices external to the controller. Examples maycomprise, but are not limited to, serial interfaces such as RS-232, USB(Universal Serial Bus) or Small Computer Systems Interface (SCSI). Thedevice specific circuits 401 provide additional hardware to enable thecontroller 400 to perform unique functions including, but not limitedto, motor control of a cartridge gripper. Moreover, the device specificcircuits 401 may include electronics that provide, by way of example butnot limitation, Pulse Width Modulation (PWM) control, Analog to DigitalConversion (ADC), Digital to Analog Conversion (DAC), etc. In addition,all or part of the device specific circuits 401 may reside outside thecontroller 400.

While the automated data storage library 10 is described as employing adistributed control system, the various approaches described and/orsuggested herein may be implemented in various automated data storagelibraries regardless of control configuration, including, but notlimited to, an automated data storage library having one or more librarycontrollers that are not distributed. Moreover, a library controller maycomprise one or more dedicated controllers of a library, depending onthe desired embodiment. For example, there may be a primary controllerand a backup controller. In addition, a library controller may compriseone or more processor nodes of a distributed control system. Accordingto one example, communication processor node 50 (e.g., of FIG. 3) maycomprise the library controller while the other processor nodes (ifpresent) may assist the library controller and/or may provide backup orredundant functionality. In another example, communication processornode 50 and work processor node 52 may work cooperatively to form thelibrary controller while the other processor nodes (if present) mayassist the library controller and/or may provide backup or redundantfunctionality. Still further, all of the processor nodes may comprisethe library controller. According to various approaches described and/orsuggested herein, a library controller may have a single processor orcontroller, or it may include multiple processors or controllers.

FIGS. SA-5B illustrate the front 501 and rear 502 views of a datastorage drive 15, according to one embodiment. In the example depictedin FIGS. 5A-5B, the data storage drive 15 comprises a hot-swap drivecanister, which is in no way intended to limit the invention. In fact,any configuration of data storage drive may be used whether or not itincludes a hot-swap canister. As discussed above, a data storage drive15 is used to read and/or write data with respect to the data storagemedia, and may additionally communicate with a memory which is separatefrom the media, and is located within the cartridge. Thus, according toone approach, a data storage cartridge may be placed into the datastorage drive 15 at opening 503.

Furthermore, FIG. 6 illustrates an embodiment of a data storagecartridge 600 with a cartridge memory 610 shown in a cutaway portion ofthe Figure, which is in no way intended to limit the invention. In fact,any configuration of data storage cartridge may be used whether or notit comprises a cartridge memory. According to various approaches, mediaof the data storage cartridge media may include any type of media onwhich data may be stored, including but not limited to magnetic media,e.g., magnetic tape, disks, etc.; optical media, e.g., optical tape,disks, etc.; electronic media, e.g., PROM, EEPROM, flash PROM,CompactFlash™, Smartmedia™, Memory Stick™, etc.; etc., or other suitablemedia. Moreover, an example of a data storage cartridge that is widelyemployed in automated data storage libraries for mass data storage is amagnetic tape cartridge in which the media is magnetic tape.

Looking now to FIGS. 7A-7B, a multi-cartridge deep slot cell 100 havingbiasing springs 152 is depicted according to one embodiment. As shown inthe illustrative embodiment, the multi-cartridge deep slot cell 100comprises a housing 110 defining an interior space 115. Furthermore, aplurality of storage slots 120 is disposed within the housing, and maybe configured for storing up to a plurality of data storage cartridges600, depending on the desired approach. Alternatively, themulti-cartridge deep slot cell 100 may be built into the frame of theautomated data storage library according to one approach.

FIGS. 8A-8D illustrate an embodiment of a cartridge blocking mechanism150 having a retaining gate 660 that retains the data storage cartridgesin the multi-cartridge deep slot cell 100 according to one embodiment.As illustrated, according to one approach, the retaining gate 660 may beexternally attached to a multi-cartridge deep slot cell 100, relative toa front opening of the multi-cartridge deep slot cell 100, whereby theretaining gate 660 can be activated by an accessor 18, e.g., of anautomated tape library. Moreover, the retaining gate 660 allows forpositive cartridge retention against the pressure of biasing springs(see 152 of FIGS. 7A-7B), and ensures that one or more data storagecartridges do not get pushed out of the multi-cartridge deep slot cell100 simultaneously, while allowing the pushing mechanism (not shown) ofthe multi-cartridge deep slot cell 100 to continuously push data storagecartridge(s) to the opening in a multi-cartridge deep slot cell 100.Thus, according to one approach, the accessor 18 may open the retaininggate to gain access to the data storage cartridge in tier 1 and, uponits extraction, the biasing spring 152 moves the cartridge(s) positionedbehind the extracted cartridge forward, thereby promoting thecartridge(s) by one tier as will soon become apparent.

The basic working of the retaining gate is that the gate prevents thedata storage cartridge(s) from being pushed out of a multi-cartridgedeep slot cell 100. For example, as shown in FIGS. 8A-8D, a retaininggate 660 can be lifted by, for example, accessor 18 or by a frontstorage cartridge 642 for cartridge removal from/insertion into amulti-cartridge deep slot cell 100. Specifically, retaining gate 660 hasa pivoting arm 661 mounted on multi-cartridge deep slot cell 100 via apivoting post (not shown) that can be integral to a construction ofmulti-cartridge deep slot cell 100. Pivoting arm 661 is located below acatch 662 of retaining gate 660 whereby a thrust force TF through datastorage cartridge 644-642 caused by the pushing mechanism (not shown) ofmulti-cartridge deep slot cell 100 causes retaining gate 660 to stayclosed in a retaining position as shown in FIG. 8A. Moreover, theretaining gate 660 is preferably biased such that it closes in thedownward direction over the front opening of multi-cartridge deep slotcell 100. This constant biasing may be achieved via gravity as shown inFIG. 8A or by implementing a spring force, e.g., attached to retaininggate 660 (not shown).

For removal of front storage cartridge 642 by accessor 18 frommulti-cartridge deep slot cell 100, retaining gate 660 must be liftedupward to a releasing position whereby catch 662 of retaining gate 660is disengaged from front storage cartridge 642. This can be seen in FIG.8B where accessor 18 interfaces with retaining gate 660 by providing alifting force. Once retaining gate 660 is lifted to the releasingposition and accessor 18 is engaged with storage cartridge 642, accessor18 can pull storage cartridge 642 out of multi-cartridge deep slot cell100 and into accessor 18 without any interference of retaining gate 660as shown in FIG. 8C. In view of storage cartridges 644 and 643 beingstored in multi-cartridge deep slot cell 100, retaining gate 660 mustreturn to its retaining position to prevent storage cartridges 644 and643 from being ejected from multi-cartridge deep slot cell 100 by thethrust force TF of the pushing mechanism (not shown). During extractionof front storage cartridge 642 through the front opening ofmulti-cartridge deep slot cell 100, the retaining gate 660, which isbeing biased downward, moves back to the retaining position to engagestorage cartridge 643.

Once front storage cartridge 642 is extracted and storage cartridges 643and 644 are retained from being pushed out of multi-cartridge deep slotcell 100, retaining gate 660 has successfully completed its cartridgeretrieval process. Now retaining gate 660 demonstrates its ability towork for cartridge insertion into multi-cartridge deep slot cell 100.When accessor 18 begins to insert storage cartridge 642 back intomulti-cartridge deep slot cell 100, retaining gate 660 is lifted to itsreleasing position to allow storage cartridge 642 through the frontopening of multi-cartridge deep slot cell 100. Catch 662 of retaininggate 660 interfaces with a rear portion of storage cartridge 642, inparticular a beveled surface of catch 662 as shown in FIG. 8D, wherebyretaining gate 660 is lifted to its releasing position as shown in FIG.8B due to storage cartridge 642 being pushed in multi-cartridge deepslot cell 100 by accessor 18. In doing so, storage cartridges 644, 643are pushed deeper into multi-cartridge deep slot cell 100 by storagecartridge 642 in multi-cartridge deep slot cell 100 by accessor 18.Thus, the accessor is able to provide a force greater than the thrustforce TF antiparallel thereto, to overcome the directional biasing ofthe storage cartridges 644, 643. Upon full insertion intomulti-cartridge deep slot cell 100, retaining gate 660 moves to itsretaining position to engage storage cartridge 642 as shown in FIG. 8A.

For a fuller understanding of the retaining gate, refer to U.S. patentapplication Ser. No. 11/674,904, which is entitled “Retaining Gate forDeep Storage Slot Retention of Storage Cartridges”, which isincorporated herein for reference.

Thus, looking to the embodiments presented herein, access to a storageslot may include the ability to remove a cartridge from a storage slot,the ability to place a cartridge into a storage slot, or combinationsthereof.

According to an exemplary embodiment, the storage slots from top tobottom are considered to be in parallel and comprise the same tier.Moreover, the storage slots from front to back, in a particular row, areconsidered to be in series and comprise sequential tiers.

Referring back to FIGS. 7A-7B, in accordance with one embodiment,storage slots 120 are depicted as being configured for storing up to aplurality of data storage cartridges 600, and arranged in sequentialorder of tiers 621, 622, 623, 624, 625 from front to rear. It should benoted that the frontmost tier 621 is also called “tier 1”, while thenext tier 622 is called “tier 2”, etc., and the last tier 625 is alsocalled the “rearmost” tier. However, referring to FIG. 2, in oneembodiment, the single cartridge storage slots 16 are also termed “tier0”.

Referring again to FIGS. 1-3, according to one embodiment, thecontroller of automated data storage library 10 may operate theaccessor(s) 18, 28 to selectively extract, place and/or transport datastorage cartridges with respect to the multi-cartridge deep slot cells100 and/or other elements of the automated data storage library 10. Forexample, the controller may facilitate extracting a cartridge from amulti-cartridge deep slot cell 100, transporting the cartridge to a datastorage drive 15 and placing the cartridge in the drive 15. Thecontroller may then extract the cartridge from the data storage drive15, while directing the accessor to transport the cartridge to aspecific multi-cartridge deep slot cell 100, and place the cartridgetherein.

In one embodiment, one or more data storage cartridges may be added intothe library, e.g., at an I/O station 24, 25, whereby the controller ofthe automated data storage library 10 may then operate the accessor(s)18, 28 to transport the cartridge(s) to specific multi-cartridge deepslot cell(s) 100, and place the cartridge(s) therein. Similarly, thecontroller may operate the accessor(s) to selectively extract, place andtransport data storage cartridges with respect to the single cartridgestorage slots 16, and/or transport inserted or added cartridge(s) tospecific single cartridge storage slots 16.

Moreover, explanation of method 750 is done with continued reference tothe storage frame 11 of FIG. 2.

Referring now to FIG. 9, method 750 illustrates an embodiment of amethod of storing data storage cartridges by an automated data storagelibrary. The method 750 may be used to selectively extract, place andtransport data storage cartridges with respect to multi-cartridge deepslot cells, where cartridges are placed in tier 1 (the frontmost tier)of a multi-cartridge deep slot cell, moving or demoting any othercartridges in the multi-cartridge deep slot cell by one tier.

The method 750 includes performing destage and/or insert moves. See step700. According to a preferred approach, insert moves comprise adding newcartridges to the library. Moreover, according to other approaches,destage moves may result from demount moves, e.g., demounting cartridgesfrom data storage drive(s) 15. In method 750, the library controlleroperates the accessor(s) to selectively extract a specific cartridgefrom one location, and transport the data storage cartridge with respectto other elements of the automated data storage library.

When the operation(s) at the data storage drive are complete, thecontroller operates the accessor(s) to return the cartridge to a storageslot 16 or to a multi-cartridge deep slot cell 100. However, if all ofthe single cartridge storage slots 16 are full, at least in theparticular frame of the library of the data storage drive 15 from whichthe data storage cartridge was previously demounted, the controller mayswap the data storage cartridge with a data storage cartridge in anotherstorage slot. Furthermore, the swapped data storage cartridge may thenbe demoted to tier 1 of a multi-cartridge deep slot cell 100, in anaction called “destage”, and the demounted cartridge is moved to thestorage slot vacated by the demoted cartridge.

As an example, which is in no way intended to limit the invention, allof the single cartridge storage slots may be full because the cartridgesmounted in the data storage drives are all from the multi-cartridge deepslot cells. Moreover, according to another approach, the movement of thedata storage cartridges may be conducted while maintaining the rearmosttier of the multi-cartridge deep slot cells vacant, called “depthspreading”.

Referring again to FIG. 9, step 701 comprises selecting themulti-cartridge deep slot cells (MCDSC) from which to make the choice ofloading for a destage or insert move, depending on step 700. One choicemay include a single column of multi-cartridge deep slot cells closestto the source of the move, which may limit the potential lateralmovement of the accessor. However, an expanded choice may be a sectionof the library encompassing more than one column. Another choice may bea frame of the library, while a last choice may be the entire library.

In a preferred approach, the library controller maintains an inventoryof cartridges and cells, and completes the selection of amulti-cartridge deep slot cell to place the added or inserted cartridgebefore movement of the accessor.

According to different approaches, at least one, some, a majority, all,etc. of the multi-cartridge deep slot cells in the chosen set may be“selected”, while the remainder may be reserved. One example comprisesreserving a multi-cartridge deep slot cell to temporarily deposit orstore data storage cartridges extracted from the front tiers of anothermulti-cartridge deep slot cell in order to access and extract acartridge towards or at the rear of that other multi-cartridge deep slotcell.

With continued reference to FIG. 9, in step 702, the library controllerdetermines whether one or more tiers in addition to the rearmost tier(e.g., 265 of FIG. 7A) is available in any of the selectedmulti-cartridge deep slot cells, or whether all tiers except therearmost tier are fill.

If at least one tier other than the rearmost tier is available, “NO”, instep 703, the library controller operates the accessor(s) to place thenext cartridge in one of the selected multi-cartridge deep slot cells,until the stage is reached where each of the frontmost tiers of theselected multi-cartridge deep slot cells become fill. According to oneapproach, the library controller may operate the accessor(s) to placedata storage cartridges in the multi-cartridge deep slot cells whilemaintaining the rearmost tier of the cells vacant. Thus, each of themulti-cartridge deep slot cells may be fill except for the rearmost tierof each of the cells.

Referring back to step 702 of FIG. 9, if all of the tiers except therearmost tier are full, “YES”, step 704 determines whether a thresholdlevel of the selected multi-cartridge deep slot cells are full,including the rearmost tier. According to one approach, the thresholdmay be considered as a determination whether a minimum level of thenumber of available positions in the rearmost tier of the selected cellshas been reached. Moreover, some positions are left available totemporarily deposit or store data storage cartridges extracted from thefront tiers of another multi-cartridge deep slot cell in order to accessand extract a cartridge towards or at the rear of that othermulti-cartridge deep slot cell.

The threshold level may, for example, be that 7/8 of the rearmost tiersof the selected set of multi-cartridge deep slot cells are full and that1/8 are vacant. In another approach, the threshold may be a specificnumber of vacancies. The threshold level, in one embodiment, may bepredetermined as based on the likely number of cartridges that will betemporarily deposited while accessing a cartridge located in a rearmosttier.

Looking again to step 704, if the threshold level of the selected set ofmulti-cartridge deep slot cells has been reached, “YES”, in step 707,the selection of multi-cartridge deep slot cells is expanded. Forexample, if the initial selection is a specific column of cells, theselection may be expanded to a number of adjacent columns of cells, tothe cells in an entire frame, to the cells of the entire library, etc.Furthermore, if step 708 indicates that the threshold level has beenreached for the maximum selection of cells, the destage or insert moveis failed in step 709. Otherwise, the process returns to step 702 wherethe expanded set of multi-cartridge deep slot cells are checked again.

According to one approach, if the library controller has determined thatall tiers of the selected multi-cartridge deep slot cells except therearmost tier are fill, e.g., in step 702, another data storagecartridge may be added to the library 10. Moreover, the added datastorage cartridge may be demoted to tier 1 in the operations ofselectively extracting, placing and transporting data storagecartridges, but is not limited thereto.

With continued reference to the method 750 of FIG. 9, when all tiersexcept the rearmost tiers are full, and the threshold level of step 704has not been reached, “NO”, in step 710, destaged or inserted datastorage cartridges are placed in selected multi-cartridge deep slotcells in tier 1 so as to demote the other cartridges in the cell. As aresult, the rearmost tier of the multi-cartridge deep slot cells arefilled, except for an evenly spread selection of the multi-cartridgedeep slot cells. In one approach, the evenly spread selection mayinclude filling the rearmost tier of multi-cartridge deep slot cellshaving vacant rearmost tiers based on a random selection. Moreover, asthe rearmost tier of one of the multi-cartridge deep slot cells isfilled, that cell is removed from the random selection.

However, according to another approach, in response to the determinationthat all tiers of the selected multi-cartridge deep slot cells 100except the rearmost tier are full, the library controller may operatethe accessor(s) to place data storage cartridges to fill the selectedmulti-cartridge deep slot cells except for the rearmost tier of everyNth selected multi-cartridge deep slot cell. As one example. “N” maycomprise a binary number beginning with “2”, or every second cell. Theselection of every second cell may begin at any arbitrary cell of thelibrary, and may comprise selecting cells to fill or cells to maintainthe rearmost tier vacant.

According to another embodiment, the library controller may employ tiebreakers as needed to place the added data storage cartridges in thefrontmost tier of the multi-cartridge deep slot cell 100 having theevery second, fourth, etc. cell that has the rearmost tier available.According to different approaches, the tie breaker may select thespecific cell based on its having the least recently used data storagecartridge in the frontmost tier and/or is at the closest proximity tothe source of the move, but is not limited thereto.

Thus, according to one approach, the method 750 of FIG. 9 may continuein binary fashion, filling and leaving vacant the rearmost tier everyeighth multi-cartridge deep slot cell 100, etc., and may ultimately fillthe rearmost tier of all multi-cartridge deep slot cells, or reach thedefined threshold of multi-cartridge deep slot cells set by the librarycontroller.

The “depth spreading” discussed above provides an evenly spreadavailability of at least the rearmost tier of a number ofmulti-cartridge deep slot cells, for example, through random selection,or by leaving the rearmost tier of every Nth one of the multi-cartridgedeep slot cells vacant. This vacant tier of a number of multi-cartridgedeep slot cells, in one embodiment, provides vacant tiers in which totemporarily store or deposit the overlying data storage cartridges togain access to the target data storage cartridge. Also, oralternatively, certain of the multi-cartridge deep slot cells or certaintiers may be reserved for the purpose of temporarily depositing datastorage cartridges overlying a target cartridge.

As described above, a controller may facilitate extracting a cartridgefrom a multi-cartridge deep slot cell, transport the cartridge to a datastorage drive and placing the cartridge in the drive, e.g., see 15 ofFIG. 2. Once in the data storage drive, data may be read from and/orwritten to tape stored in the cartridge.

However, conventional products have been plagued with data lossresulting from unintentional overwrites of data stored on tape incartridges. Specifically, problems have occurred when a first host (HostA) writes to a drive and a second host (Host B) issues a rewind requestto the same drive. The drive performs the rewind as instructed by HostB, after which Host A continues writing. Host A is not aware that thetape location has changed as a result of the drive performing the rewindrequest, and as a result, the continued writing overwrites previouslywritten tracks beginning at the location the tape has been rewound to.Moreover, data that is overwritten is usually unrecoverable, and in someinstances may compromise the entirety of the data stored on theremainder of the tape. For example, if a conventional product overwrites25 data blocks on a 4 Terabyte (TB) tape, the entire 4 TB of data may belost.

Attempts to overcome this issue have been implemented in IO drivers,software, tape management system software, etc. of conventionalproducts, but have proven to be unsuccessful. In sharp contrast, variousembodiments herein are desirably able to protect data stored on magnetictape from being overwritten as a result of intermittent rewind commandsbeing performed while writing to the tape. Specifically, by determininga current location of tape relative to a set of transducers, it may bedetermined if a pending write operation will be performed in a desiredlocation on the tape, as will be described in further detail below.

Tape drives and code embodied therewith are able to determine what thedata corresponding to pending write requests includes when the requestsare received. As a result, tape drives and code embodied therewith maybe able to determine if a write command has been issued, and if so,whether the drive is located at a block at which it is appropriate toperform the write request. For example, if the tape drive is located ata block at the beginning of tape, the data to be written desirablymatches the size and type specified for the block at the beginning ofthe tape.

Referring now to FIG. 10, a flowchart of a method 1000 is shownaccording to one embodiment. The method 1000 may be performed inaccordance with the present invention in any of the environmentsdepicted in FIGS. 1-9, among others, in various embodiments. Of course,more or less operations than those specifically described in FIG. 10 maybe included in method 1000, as would be understood by one of skill inthe art upon reading the present descriptions.

Each of the steps of the method 1000 may be performed by any suitablecomponent of the operating environment. For example, in variousembodiments, the method 1000 may be partially or entirely performed by acontroller, a driver, or some other device having one or more processorstherein. The processor, e.g., processing circuit(s), chip(s), and/ormodule(s) implemented in hardware and/or software, and preferably havingat least one hardware component may be utilized in any device to performone or more steps of the method 1000. Illustrative processors include,but are not limited to, a central processing unit (CPU), an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA), etc., combinations thereof, or any other suitable computingdevice known in the art.

Further still, any one or more of the operations of method 1000 may beimplemented in one or more tape drives using microcode embodiedtherewith. In some approaches, one or more of the operations of method1000 may be implemented in a system having a processor and logicintegrated with and/or executable by the processor, the logic beingconfigured to perform the one or more operations of method 1000. Itfollows that any of the approaches described herein may be applied tophysical and/or logical tape systems depending on the desiredembodiment.

Referring now to FIG. 10, method 1000 begins with operation 1002 whichincludes receiving a write command to write to a magnetic tape. Thewrite command may come from a host, computer, etc. and may include datato be written to the tape.

Operation 1004 includes determining a current location of the magnetictape relative to transducers intended to perform the write command. Itfollows that, referring to the present description, the “currentlocation” may be the location where the writing requested by the writecommand will be performed if allowed. The current location may bedetermined in any conventional manner, such as by reading LinearPosition (LPOS) data from the servo tracks of the tape, determining ablock identifier of the last written data block and/or of the data blockto be written, etc.

Method 1000 further includes determining whether the current location ofthe magnetic tape is at a block at a beginning of tape, as seen inoperation 1006.

If operation 1006 determines that the current location is not at a blockat the beginning of tape, method 1000 proceeds to operation 1012 whichallows execution of the write command.

However, if it is determined that the current location is at a block atthe beginning of tape, method 1000 proceeds to operation 1008 whichincludes determining whether the data corresponding to the write commandis at least one of: a size and type specified for the block. Accordingto some approaches, the type of the data may correspond to a volumeidentifier (VOLID) as will soon become apparent.

The first three takes of each partition in standard volume magneticrecording tapes typically include three 80 byte character blocks ofdata, each of which are represented by a block identifier (Block ID).The first 80 byte character block of data Block ID-0 includes a VOLIDwhich is used to identify the cartridge and tape stored therein.Moreover, following Block ID-0 are Block ID-1 and Block ID-2, each ofwhich contain a header.

The VOLID for a given tape usually includes, but is not limited to, asix character name which may be encoded on the tape (e.g., for the tapedrive to read) as well as the outside of the tape cartridge (e.g., forhumans to read). Thus, when a read request is being processed, the driveis able to ensure that the cartridge mounted in the drive is the onethat was actually requested by reading the VOLID. If the tape managementsoftware verifies that the VOLID read from the tape corresponds to whatwas actually requested, the drive may be permitted to run any desiredprogram.

Following the three 80 byte character blocks of data at the beginning oftape, data is written in much larger blocks. For example, which is in noway intended to limit the invention, depending on the embodiment, datamay be written to a magnetic tape in 16k, 32k, 64k, 128k, etc. blocks.In other words, data written to tape following the initial three blocksof data are not written in character blocks of a byte size correspondingto current and/or previous standard volume label rules. Thus, the sizespecified for a block at the beginning of tape may be different than asize specified for a user data block located after any initialpredefined and/or preassigned blocks of data. Furthermore, according tovarious approaches, any VOLID and/or block size specified by the labelrules for the format of the data written to the tape may be imposeddepending on the desired embodiment.

Referring still to method 1000 of FIG. 10, if it is determined that thedata corresponding to the write command is not of the specified sizeand/or type specified for the block, operation 1010 includes disallowingexecution of the write command received in operation 1002. Thus,according to some approaches, execution of the write command may bedisallowed if data corresponding to the write command is either not ofthe specified size or not of the specified type, while according toother approaches, execution of the write command may be disallowed ifdata corresponding to the write command is not of the specified size andtype. Examples of further operations in response to disallowingexecution of the write command are presented below.

Alternatively, if it is determined in operation 1008 that the datacorresponding to the write command is of the specified size and/or typespecified for the block, method 1000 proceeds to operation 1012 whichallows execution of the write command.

Following the examples provided above, method 1000 may be implemented inan embodiment in which requests corresponding to a given tape arereceived from two different hosts: Host A and Host B. According to onesuch approach, which is in no way intended to limit the invention, thewrite command received in operation 1002 may be received from Host A.However, the current location of the magnetic tape may be at a block atthe beginning of the tape, e.g., due to a rewind command received fromHost B and implemented by the tape drive between write operations of thewrite command. As a result, data corresponding to the write command fromHost A would not correspond to a specified size and/or type specifiedfor the block at the current location, and the write operation would berejected.

It follows that various embodiments described herein preferably includedrive microcode which includes a selectable operation mode which is ableto determine when a current location is at the beginning of a tape.Moreover, the microcode is preferably able to disallow any writecommands received that do not match the type and/or size of writecommands corresponding to the first three blocks of the currentpartition of tape, e.g., in order to protect data previously written tothe tape from being overwritten.

In other words, if the current location corresponds to any of BlockID-0, Block ID-1, or Block ID-2 and a pending write request includeswriting anything other than a block of data corresponding to the sizeand/or type of that corresponding to Block ID-0, Block ID-1, and BlockID-2, the write operation will fail. Thus, if the block corresponding tothe current location of the magnetic tape is a first block on thepresent partition of the tape, user write requests are preferably deniedas the data corresponding to the requests will not correspond to a sizeor type specified for the first block. According to an exemplary in-useembodiment which is in no way intended to limit the invention, only 80byte character records may be written to Block ID-0, block ID-1, andblock ID-2.

Upon rejecting a write operation, e.g., for reasons described herein andthose similar thereto, a tape drive may inform a host of the rejection.According to some approaches, a notification may be sent to the hostfrom which the write operation was received. However, in otherapproaches, a notification may be sent to an administrator, a systemmanager, stored in memory (e.g., a lookup table), etc.

The notification may be in the form of a unit check sent from the tapedrive where the rejection occurred. Moreover, in some approaches, theunit check may include a fault system code which includes a systemmessage that indicates the cause of the failure. However, in order topresent meaningful information to a host, e.g., such as a fault systemcode, additional software changes may be implemented in the drive.

After a failure has been detected, the corresponding tape drive mayremain at the location on the tape where the failure was detected untilany further instructions are received. For example, host recoveryefforts and/or system software may determine any post-failure operationsfor the tape drive to perform. However, in other approaches, thecartridge containing the tape on which the failure occurred may simplybe removed from the tape drive. It should also be noted that any of theapproaches described herein may be applied to physical and/or logicaltape systems depending on the desired embodiment.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

A data processing system suitable for storing and/or executing programcode may include at least one processor, which may be or be part of acontroller, coupled directly or indirectly to memory elements through asystem bus, such as controller 400 of FIG. 4. The memory elements caninclude local memory employed during actual execution of the programcode, such as nonvolatile memory 404 of FIG. 4, bulk storage, and cachememories which provide temporary storage of at least some program codein order to reduce the number of times code must be retrieved from bulkstorage during execution.

Moreover, the flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

It will be further appreciated that embodiments of the present inventionmay be provided in the form of a service deployed on behalf of acustomer. Those of skill in the art will understand that changes may bemade with respect to the methods discussed above, including changes tothe ordering of the choices of the methods of FIG. 9. Further, those ofskill in the art will understand that differing specific componentarrangements may be employed than those illustrated herein.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of an embodiment of the presentinvention should not be limited by any of the above-described exemplaryembodiments, but should be defined only in accordance with the followingclaims and their equivalents.

What is claimed is:
 1. A method, comprising: receiving a write commandto write to a magnetic tape; determining whether a current location ofthe magnetic tape is at a block at a beginning of tape; determiningwhether data corresponding to the write command is at least one of: asize and type specified for the block; and disallowing execution of thewrite command when the data corresponding to the write command is not ofthe specified size and/or type.
 2. A method as recited in claim 1,wherein the type of the data corresponds to a volume identifier.
 3. Amethod as recited in claim 1, wherein the size specified for the blockis different than a size specified for a user data block.
 4. A method asrecited in claim 1, wherein the block is a first block on the tape.
 5. Amethod as recited in claim 1, wherein execution of the write command isdisallowed when the data corresponding to the write command is not ofthe specified size and type.
 6. A method as recited in claim 1, whereinthe method is performed in a tape drive.
 7. A method as recited in claim6, wherein the write command is received from a first host, wherein thecurrent location of the magnetic tape is at the block at a beginning oftape because of a rewind command received from a second host.
 8. Asystem, comprising: a processor and logic integrated with and/orexecutable by the processor, the logic being configured to: receive awrite command to write to a magnetic tape; determine whether a currentlocation of the magnetic tape is at a block at a beginning of tape;determine whether data corresponding to the write command is at leastone of: a size and type specified for the block; and disallow executionof the write command when the data corresponding to the write command isnot of the specified size and/or type.
 9. A system as recited in claim8, wherein the type of the data corresponds to a volume identifier. 10.A system as recited in claim 8, wherein the size specified for the blockis different than a size specified for a user data block.
 11. A systemas recited in claim 8, wherein the block is a first block on the tape.12. A system as recited in claim 8, wherein execution of the writecommand is disallowed when the data corresponding to the write commandis not of the specified size and type.
 13. A system as recited in claim8, comprising a tape drive having or in communication with theprocessor.
 14. A system as recited in claim 13, wherein the writecommand is received from a first host, wherein the current location ofthe magnetic tape is at the block at a beginning of tape because of arewind command received from a second host.
 15. A system as recited inclaim 8, comprising: a drive mechanism for passing a magnetic mediumover a magnetic head; and a controller electrically coupled to themagnetic head, the processor being part of the controller.
 16. Acomputer program product comprising a computer readable storage mediumhaving program instructions embodied therewith, the program instructionsreadable and/or executable by a hardware controller to cause thecontroller to: receive, by the controller, a write command to write to amagnetic tape; determine, by the controller, whether a current locationof the magnetic tape is at a block at a beginning of tape; determine, bythe controller, whether data corresponding to the write command is atleast one of: a size and type specified for the block; and disallow, bythe controller, execution of the write command when the datacorresponding to the write command is not of the specified size and/ortype.
 17. A computer program product as recited in claim 16, wherein thetype of the data corresponds to a volume identifier.
 18. A computerprogram product as recited in claim 16, wherein the size specified forthe block is different than a size specified for a user data block. 19.A computer program product as recited in claim 16, wherein the block isa first block on the tape.
 20. A computer program product as recited inclaim 16, wherein the write command is received from a first host,wherein the current location of the magnetic tape is at the block at abeginning of tape because of a rewind command received from a secondhost.